Systems and methods using a cloud proxy for mobile device management and policy

ABSTRACT

Systems and methods include, in a cloud node, receiving Mobile Device Management (MDM) data from a central authority, wherein the MDM data includes policy metadata specifying MDM functions for mobile devices associated with users of an enterprise; communicating to an application on a mobile device associated with a user, via a tunnel, wherein the application is configured for service discovery and connectivity; and providing the MDM data to the mobile device associated with the user via the tunnel.

CROSS-REFERENCE TO RELATED APPLICATION(S)

The present patent application/patent is a continuation-in-part of U.S. patent application Ser. No. 15/900,951, filed Feb. 21, 2018, and entitled “SYSTEMS AND METHODS FOR CLOUD BASED UNIFIED SERVICE DISCOVERY AND SECURE AVAILABILITY,” which is a continuation of U.S. patent application Ser. No. 15/153,108 filed May 12, 2016 (now U.S. Pat. No. 9,935,955, issued on Apr. 3, 2018), and entitled “SYSTEMS AND METHODS FOR CLOUD BASED UNIFIED SERVICE DISCOVERY AND SECURE AVAILABILITY,” which claims the benefit of priority of Indian Patent Application No. 201611010521, filed on Mar. 28, 2016, and entitled “SYSTEMS AND METHODS FOR CLOUD BASED UNIFIED SERVICE DISCOVERY AND SECURE AVAILABILITY,” the contents of each are incorporated in full by reference herein.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to computer networking systems and methods. More particularly, the present disclosure relates to systems and methods using a cloud proxy for mobile device management and policy.

BACKGROUND OF THE DISCLOSURE

There is a staggering growth of endpoint mobile devices in enterprises. With this influx, enterprise Information Technology (IT) administrators can no longer ignore these mobile devices as simply outside their scope of responsibility. Correspondingly, there has been an unprecedented growth in the cloud services that are made available by an enterprise to its employees. Traditionally, enterprises have deployed one secure application for each service for each platform, but this has eventually failed to scale with the growth of mobility in IT. There are myriad numbers of cloud-based services that are being accessed from unmanaged endpoint mobile devices across diverse operating systems, uncontrolled network topologies and vaguely understood mobile geographies. Typically, enterprises have deployed applications for a specific service, applications to access corporate resources that themselves vary for different network conditions, and applications to secure the endpoints itself.

Conventionally, for each application, the enterprise user has to perform numerous steps. For example, the end user has to contact an enterprise administrator (i.e., in person or web portal) to configure the mobile device to use the end-point application for a corresponding service. The end user has to enroll in each application to access a service, and the enterprise administrator has to undertake to the complex tasks of tracking, deploying and managing individual apps on each endpoint mobile device. Accordingly, it would be advantageous to eliminate the multiple applications for various enterprise functions, to enable a user to connect to multiple cloud services.

Normally, in order to securely access multiple network resources concurrently, the end user has to connect to multiple applications, such as a corporate Virtual Private Network (VPN) for accessing enterprise's internal resources (intranet) and a private VPN or a network filtering application for accessing internet resources. This is not only perplexing for the end user but also creates several compatibility issues between different applications which compete for network access at different layers of networking. For instance, the service of a VPN application to securely connect to an enterprise network is affected by a web security firewall application running on the device which monitors and forbids any network interface changes. The situation is further exacerbated by the fact that the user needs to reconfigure each application depending upon the changes in network conditions such as moving from one subnet to another and that there is no indication to the user to perform such a change. All such service transitions must then be performed manually by the user with every network change. This is analogous to the situation where a user must statically configure Internet Protocol (IP) address configuration on a network interface for every network change. This problem was overcome by Dynamic Host Configuration Protocol (DHCP) that discovers configuration for the interface such as IP Address, Subnet Mask, Default Gateways and Domain Name System (DNS) servers. With the advent of mobility and explosion in the number of cloud services and mobile applications, there is a similar need for unified service discovery and secure availability.

Additionally, Mobile Device Management (MDM) has been a challenging task for IT. As is known in the art, MDM is an industry term for the administration of mobile devices, such as smartphones, tablet computers, and laptops. MDM is typically a deployment of a combination of on-device applications and configurations, corporate policies and certificates, for the purpose of simplifying and enhancing the IT management of end user devices. In modern corporate IT environments, the sheer number and diversity of managed devices (and user behavior) has motivated MDM solutions that allow the management of devices and users in a consistent and scalable way. The overall role of MDM is to increase device supportability, security, and corporate functionality while maintaining some user flexibility. MDM primarily deals with corporate data segregation, securing emails, securing corporate documents on devices, enforcing corporate policies, integrating and managing mobile devices including laptops and handhelds of various categories.

Some of the core functions of MDM include:

Ensuring that diverse user equipment is configured to a consistent standard/supported set of applications, functions, or corporate policies;

Updating equipment, applications, functions, or policies in a scalable manner;

Ensuring that users use applications in a consistent and supportable manner;

Ensuring that equipment performs consistently;

Monitoring and tracking equipment (e.g., location, status, ownership, activity); and

Being able to efficiently diagnose and troubleshoot equipment remotely

As mobile devices proliferate, it becomes difficult to track and enforce IT policies on mobile devices. Traditionally, IT has to install a separate client application on a mobile device, which calls home to get the latest IT policies and then enforce it on device. The client application requires to check frequently with a policy server for any update. Or it must subscribe to push notification services to get notified when to check for new updates. Both these approaches are resource intensive and requires a lot of scalability.

BRIEF SUMMARY OF THE DISCLOSURE

The present disclosure relates to systems and methods using a cloud proxy for mobile device management and policy. In particular, the present disclosure utilizes an application executed on a user device, for cloud service discovery and connectivity, to also provide Mobile Device Management (MDM) functionality. The application is required on a user device to access enterprise, cloud-based resources. Thus, this approach removes the requirement for enterprise IT to install a separate client to manage IT policies. This approach saves memory and precious device battery. The solution is highly scalable and efficient, as it does not require the client application to call home or subscribe to any notification service.

In an embodiment, a method in a cloud node includes receiving Mobile Device Management (MDM) data from a central authority, wherein the MDM data includes policy metadata specifying MDM functions for mobile devices associated with users of an enterprise; communicating to an application on a mobile device associated with a user, via a tunnel, wherein the application is configured for service discovery and connectivity; and providing the MDM data to the mobile device associated with the user via the tunnel. In another embodiment, a cloud node includes a processor and memory storing instructions that, when executed, cause the processor to receive Mobile Device Management (MDM) data from a central authority, wherein the MDM data includes policy metadata specifying MDM functions for mobile devices associated with users of an enterprise; communicate to an application on a mobile device associated with a user, via a tunnel, wherein the application is configured for service discovery and connectivity; and provide the MDM data to the mobile device associated with the user via the tunnel.

In an embodiment, a method implemented by an application executed on a user device for service discovery and connectivity includes discovering one or more cloud services for a user associated with the user device; creating and operating an interface on the user device; and intercepting traffic at the interface from one or more client applications on the user device and splitting the traffic based on configuration to the one or more cloud services.

In another embodiment, a user device configured to execute an application for service discovery and connectivity includes a network interface, a data store, and a processor communicatively coupled to one another; and memory storing computer executable instructions, and in response to execution by the processor, the computer-executable instructions cause the processor to discover one or more cloud services for a user associated with the mobile device; create and operate an interface on the mobile device connected to the network interface; and intercept traffic at the interface from one or more client applications on the mobile device and split the traffic based on configuration to the one or more cloud services.

In a further embodiment, a non-transitory computer readable medium storing computer executable instructions, and in response to execution by the processor, the computer-executable instructions cause a processor to perform the steps of discovering one or more cloud services for a user associated with the user device; creating and operating an interface on the user device; and intercepting traffic at the interface from one or more client applications on the user device and splitting the traffic based on configuration to the one or more cloud services.

In an embodiment, a method, implemented by a unified agent application executed on a mobile device, for unified service discovery and secure availability includes authenticating a user into a plurality of cloud services including a proxy service and a Virtual Private Network (VPN) service, wherein the proxy service is utilized for Internet traffic and the VPN service is for Intranet traffic; creating and operating a link local network at the mobile device with a virtual network interface and multiple listening sockets; and intercepting traffic at the virtual network interface from one or more client applications on the mobile device and splitting the traffic between the proxy service, the VPN service, and the Internet based on a type of the traffic, a destination, and the one or more client applications.

In another embodiment, a mobile device configured to provide unified service discovery and secure availability through a unified agent application includes a network interface, a data store, and a processor communicatively coupled to one another; and memory storing computer executable instructions, and in response to execution by the processor, the computer-executable instructions cause the processor to authenticate a user into a plurality of cloud services including a proxy service and a Virtual Private Network (VPN) service, wherein the proxy service is utilized for Internet traffic and the VPN service is for Intranet traffic; create and operate a link local network at the mobile device with a virtual network interface and multiple listening sockets; and intercept traffic at the virtual network interface from one or more client applications on the mobile device and split the traffic between the proxy service, the VPN service, and the Internet based on a type of the traffic, a destination, and the one or more client applications.

In a further embodiment, a cloud system includes a plurality of cloud nodes, where each of the plurality of cloud nodes is configured to, for a user with a user device executing a unified agent application, authenticate the user into a plurality of cloud services including a proxy service and a Virtual Private Network (VPN) service, wherein the proxy service is utilized for Internet traffic and the VPN service is for Intranet traffic; receive traffic from the user device, wherein the unified agent application is configured to create and operate a link local network at the user device with a virtual network interface and multiple listening sockets; and direct the traffic to the Internet or an Intranet based on which tunnel the traffic is received on, wherein the unified agent application is configured to intercept traffic at the virtual network interface from one or more client applications on the user device and split the traffic between tunnels for the proxy service, the VPN service, and the Internet based on a type of the traffic, a destination, and the one or more client applications.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated and described herein with reference to the various drawings, in which like reference numbers are used to denote like system components/method steps, as appropriate, and in which:

FIG. 1 is a network diagram of a distributed security system;

FIG. 2 is a network diagram of the distributed security system of FIG. 1 illustrating various components in more detail;

FIG. 3 is a block diagram of a server which may be used in the distributed security system of FIG. 1 or with any other cloud-based system;

FIG. 4 is a block diagram of a mobile device which may be used in the system of FIG. 1 or with any other cloud-based system;

FIG. 5 is a network diagram of a generalized cloud-based system;

FIG. 6 is a network diagram of a network with a distributed security cloud providing DNS augmented security;

FIG. 7 is a network diagram of a unified agent application and associated connectivity and functionality in a network;

FIG. 8 is a network diagram of the workflow of the unified agent application in the network of FIG. 7;

FIG. 9 is a flow diagram of an event sequence associated with the unified agent application in the network of FIG. 7;

FIG. 10 is a logical diagram of functional components of the unified agent application;

FIG. 11 is a screenshot of a login screen of the unified agent application;

FIG. 12 is a screenshot of an admin dashboard for the unified agent application;

FIG. 13 is a screenshot of a network evaluation configuration for the unified agent application;

FIG. 14 is a flowchart of a proxy authentication method to the security cloud;

FIG. 15 is a flowchart of a VPN authentication method to the security cloud;

FIG. 16 is a flowchart of a device enrollment method for the client device and the unified agent application;

FIG. 17 is a flowchart of a traffic interception method implemented through the unified agent application;

FIG. 18 is a flow diagram of traffic interception and splitting using the unified agent application;

FIG. 19 is a flow diagram of example functionality of client applications, the TUN interface, sockets, and the VPN server for the interception and splitting using the unified agent application;

FIG. 20 is a flow diagram of tunnel forwarding rules by the unified agent application; and

FIG. 21 is a flowchart of an MDM method implemented through the unified agent application and the distributed security system or the cloud system.

DETAILED DESCRIPTION OF THE DISCLOSURE

The present disclosure relates to systems and methods using a cloud proxy for mobile device management and policy. In particular, the present disclosure utilizes an application executed on a user device, for cloud service discovery and connectivity, to also provide Mobile Device Management (MDM) functionality. The application is required on a user device to access enterprise, cloud-based resources. Thus, this approach removes the requirement for enterprise IT to install a separate client to manage IT policies. This approach saves memory and precious device battery. The solution is highly scalable and efficient, as it does not require the client application to call home or subscribe to any notification service.

Also, in various embodiments, the present disclosure relates to systems and methods for cloud-based unified service discovery and secure availability. The systems and methods enable a user to connect to multiple cloud services through the dynamic discovery of available services followed by authentication and access as exposed in the corresponding service protocol. The systems and methods address the unmanageable growth of mobility and cloud-based services which have led to a proliferation of individual applications for access to individual services. The systems and method can be implemented through a mobile application (“app”) which overcomes the hassle of deploying and managing several applications across a gamut of mobile devices, operating systems, and mobile networks to gain secure access to the cloud-based internet or intranet resources. The mobile application can uniquely perform a Dynamic evaluation of Network and Service Discovery, Unified Enrollment to all services, Application dependent service enablement, Service protocol learning, Service Availability through secure network traffic forwarding tunnels, and the like.

Again, enterprises have a strong need to provide secure access to cloud services to its end users. The growth of mobility and cloud in the IT enterprise has made it impossible for IT admins to deploy individual applications for individual services. The mobile app associated with the systems and methods overcomes these limitations through the dynamic discovery of available services to the end user, followed by authentication and access to individual services. Further, the mobile app insightfully learns the protocol for each service and establishes a secure tunnel to the service. In essence, the mobile app is one app that an enterprise may use to provide secure connectivity to the Internet and diversified internal corporate applications. At the time of user enrollment, the mobile app will discover all services provided by the enterprise cloud and will enroll the user to all of those services. It will then set up secure tunnels for each application depending upon whether the application is internet bound or if it is internal to the corporate network (intranet).

The mobile app will also discover all applications provided within the enterprise cloud along with a Global Virtual Private Network (GVPN) service and show the available services to end user. Endpoint Applications today provide one service for a specific network function (such as Virtual Private Network (VPN) to a corporate network, web security, antivirus to access the Internet). The mobile app can be used to enable all these services with single enrollment. The mobile app will provide services to darknet applications along with securing the Internet traffic. The mobile app can set up a local network on the mobile device.

Example High-Level System Architecture—Cloud-Based Security System

FIG. 1 is a block diagram of a distributed security system 100. The system 100 may, for example, be implemented as an overlay network in a wide area network (WAN), such as the Internet, a local area network (LAN), or the like. The system 100 includes processing nodes (PN) 110, that proactively detect and preclude the distribution of security threats, e.g., malware, spyware, viruses, email spam, Data Leakage Prevention (DLP), content filtering, etc., and other undesirable content sent from or requested by an external system. The processing nodes 110 can also log activity and enforce policies, including logging changes to the various components and settings in the system 100. Example external systems may include an enterprise or external system 200, a computer device 220, and a mobile device 230, or other network and computing systems communicatively coupled to the system 100. In an embodiment, each of the processing nodes 110 may include a decision system, e.g., data inspection engines that operate on a content item, e.g., a web page, a file, an email message, or some other data or data communication that is sent from or requested by one of the external systems. In an embodiment, all data destined for or received from the Internet is processed through one of the processing nodes 110. In another embodiment, specific data specified by each external system, e.g., only email, only executable files, etc., is process through one of the processing node 110.

Each of the processing nodes 110 may generate a decision vector D=[d1, d2, . . . , dn] for a content item of one or more parts C=[c1, c2, . . . , cm]. Each decision vector may identify a threat classification, e.g., clean, spyware, malware, undesirable content, innocuous, spam email, unknown, etc. For example, the output of each element of the decision vector D may be based on the output of one or more data inspection engines. In an embodiment, the threat classification may be reduced to a subset of categories, e.g., violating, non-violating, neutral, unknown. Based on the subset classification, the processing node 110 may allow distribution of the content item, preclude distribution of the content item, allow distribution of the content item after a cleaning process, or perform threat detection on the content item. In an embodiment, the actions taken by one of the processing nodes 110 may be determinative on the threat classification of the content item and on a security policy of the external system to which the content item is being sent from or from which the content item is being requested by. A content item is violating if, for any part C=[c1, c2, . . . , cm] of the content item, at any of the processing nodes 110, any one of the data inspection engines generates an output that results in a classification of “violating.”

Each of the processing nodes 110 may be implemented by one or more of computer and communications devices, e.g., server computers, gateways, switches, etc., such as the server 300 described in FIG. 3. In an embodiment, the processing nodes 110 may serve as an access layer 150. The access layer 150 may, for example, provide external system access to the security system 100. In an embodiment, each of the processing nodes 110 may include Internet gateways and one or more servers, and the processing nodes 110 may be distributed through a geographic region, e.g., throughout a country, region, campus, etc. According to a service agreement between a provider of the system 100 and an owner of an external system, the system 100 may thus provide security protection to the external system at any location throughout the geographic region.

Data communications may be monitored by the system 100 in a variety of ways, depending on the size and data requirements of the external system. For example, an enterprise 200 may have multiple routers, switches, etc. that are used to communicate over the Internet, and the routers, switches, etc. may be configured to establish communications through the nearest (in traffic communication time, for example) processing node 110. A mobile device 230 may be configured to communicate to the nearest processing node 110 through any available wireless access device, such as an access point, or a cellular gateway. A single computer device 220, such as a consumer's personal computer, may have its browser and email program configured to access the nearest processing node 110, which, in turn, serves as a proxy for the computer device 220. Alternatively, an Internet provider may have all of its customer traffic processed through the processing nodes 110.

In an embodiment, the processing nodes 110 may communicate with one or more authority nodes (AN) 120, which can also be referred to as a central authority (CA) node. The authority nodes 120 may store policy data for each external system and may distribute the policy data to each of the processing nodes 110. The policy may, for example, define security policies for a protected system, e.g., security policies for the enterprise 200. Example policy data may define access privileges for users, websites and/or content that is disallowed, restricted domains, etc. The authority nodes 120 may distribute the policy data to the processing nodes 110. In an embodiment, the authority nodes 120 may also distribute threat data that includes the classifications of content items according to threat classifications, e.g., a list of known viruses, a list of known malware sites, spam email domains, a list of known phishing sites, etc. The distribution of threat data between the processing nodes 110 and the authority nodes 120 may be implemented by push and pull distribution schemes described in more detail below. In an embodiment, each of the authority nodes 120 may be implemented by one or more computer and communication devices, e.g., server computers, gateways, switches, etc., such as the server 300 described in FIG. 3. In some embodiments, the authority nodes 120 may serve as an application layer 170. The application layer 170 may, for example, manage and provide policy data, threat data, and data inspection engines and dictionaries for the processing nodes 110.

Other application layer functions may also be provided in the application layer 170, such as a user interface (UI) front-end 130. The user interface front-end 130 may provide a user interface through which users of the external systems may provide and define security policies, e.g., whether email traffic is to be monitored, whether certain websites are to be precluded, etc. Another application capability that may be provided through the user interface front-end 130 is security analysis and log reporting. The underlying data on which the security analysis and log reporting functions operate are stored in logging nodes (LN) 140, which serve as a data logging layer 160. Each of the logging nodes 140 may store data related to security operations and network traffic processed by the processing nodes 110 for each external system. In an embodiment, the logging node 140 data may be anonymized so that data identifying an enterprise is removed or obfuscated. For example, identifying data may be removed to provide an overall system summary of security processing for all enterprises and users without revealing the identity of any one account. Alternatively, identifying data may be obfuscated, e.g., provide a random account number each time it is accessed, so that an overall system summary of security processing for all enterprises and users may be broken out by accounts without revealing the identity of any one account. In another embodiment, the identifying data and/or logging node 140 data may be further encrypted, e.g., so that only the enterprise (or user if a single user account) may have access to the logging node 140 data for its account. Other processes of anonymizing, obfuscating, or securing logging node 140 data may also be used. Note, as described herein, the systems and methods for tracking and auditing changes in a multi-tenant cloud system can be implemented in the data logging layer 160, for example.

In an embodiment, an access agent 180 may be included in the external systems. For example, the access agent 180 is deployed in the enterprise 200. The access agent 180 may, for example, facilitate security processing by providing a hash index of files on a client device to one of the processing nodes 110, or may facilitate authentication functions with one of the processing nodes 110, e.g., by assigning tokens for passwords and sending only the tokens to a processing node so that transmission of passwords beyond the network edge of the enterprise is minimized. Other functions and processes may also be facilitated by the access agent 180. In an embodiment, the processing node 110 may act as a forward proxy that receives user requests to external servers addressed directly to the processing node 110. In another embodiment, the processing node 110 may access user requests that are passed through the processing node 110 in a transparent mode. A protected system, e.g., enterprise 200, may, for example, choose one or both of these modes. For example, a browser may be configured either manually or through the access agent 180 to access the processing node 110 in a forward proxy mode. In the forward proxy mode, all accesses are addressed to the processing node 110.

In an embodiment, an enterprise gateway may be configured so that user requests are routed through the processing node 110 by establishing a communication tunnel between enterprise gateway and the processing node 110. For establishing the tunnel, existing protocols such as generic routing encapsulation (GRE), layer two tunneling protocol (L2TP), or other Internet Protocol (IP) security protocols may be used. In another embodiment, the processing nodes 110 may be deployed at Internet service provider (ISP) nodes. The ISP nodes may redirect subject traffic to the processing nodes 110 in a transparent proxy mode. Protected systems, such as the enterprise 200, may use a multiprotocol label switching (MPLS) class of service for indicating the subject traffic that is to be redirected. For example, at the within the enterprise, the access agent 180 may be configured to perform MPLS labeling. In another transparent proxy mode embodiment, a protected system, such as the enterprise 200, may identify the processing node 110 as a next hop router for communication with the external servers.

Generally, the distributed security system 100 may generally refer to an example cloud-based security system. Other cloud-based security systems and generalized cloud-based systems are contemplated for the systems and methods for tracking and auditing changes in a multi-tenant cloud system. Cloud computing systems and methods abstract away physical servers, storage, networking, etc. and instead offer these as on-demand and elastic resources. The National Institute of Standards and Technology (NIST) provides a concise and specific definition which states cloud computing is a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. Cloud computing differs from the classic client-server model by providing applications from a server that are executed and managed by a client's web browser, with no installed client version of an application required. Centralization gives cloud service providers complete control over the versions of the browser-based applications provided to clients, which removes the need for version upgrades or license management on individual client computing devices. The phrase “software as a service” (SaaS) is sometimes used to describe application programs offered through cloud computing. A common shorthand for a provided cloud computing service (or even an aggregation of all existing cloud services) is “the cloud.” The distributed security system 100 is illustrated herein as one example embodiment of a cloud-based system, and those of ordinary skill in the art will recognize the tracking and auditing systems and methods contemplate operation on any cloud-based system.

Example Detailed System Architecture and Operation

FIG. 2 is a block diagram of various components of the distributed security system 100 in more detail. Although FIG. 2 illustrates only one representative component processing node 110, authority node 120 and logging node 140, those of ordinary skill in the art will appreciate there may be many of each of the component nodes 110, 120 and 140 present in the system 100. A wide area network (WAN) 101, such as the Internet, or some other combination of wired and/or wireless networks, communicatively couples the processing node 110, the authority node 120, and the logging node 140 to one another. The external systems 200, 220 and 230 likewise communicate over the WAN 101 with each other or other data providers and publishers. Some or all of the data communication of each of the external systems 200, 220 and 230 may be processed through the processing node 110.

FIG. 2 also shows the enterprise 200 in more detail. The enterprise 200 may, for example, include a firewall (FW) 202 protecting an internal network that may include one or more enterprise servers 216, a lightweight directory access protocol (LDAP) server 212, and other data or data stores 214. Another firewall 203 may protect an enterprise subnet that can include user computers 206 and 208 (e.g., laptop and desktop computers). The enterprise 200 may communicate with the WAN 101 through one or more network devices, such as a router, gateway, switch, etc. The LDAP server 212 may store, for example, user login credentials for registered users of the enterprise 200 system. Such credentials may include a user identifier, login passwords, and a login history associated with each user identifier. The other data stores 214 may include sensitive information, such as bank records, medical records, trade secret information, or any other information warranting protection by one or more security measures.

In an embodiment, a client access agent 180 a may be included on a client computer 206. The client access agent 180 a may, for example, facilitate security processing by providing a hash index of files on the user computer 206 to a processing node 110 for malware, virus detection, etc. Other security operations may also be facilitated by the access agent 180 a. In another embodiment, a server access agent 180 may facilitate authentication functions with the processing node 110, e.g., by assigning tokens for passwords and sending only the tokens to the processing node 110 so that transmission of passwords beyond the network edge of the enterprise 200 is minimized. Other functions and processes may also be facilitated by the server access agent 180 b. The computer device 220 and the mobile device 230 may also store information warranting security measures, such as personal bank records, medical information, and login information, e.g., login information to the computers 206 of the enterprise 200, or to some other secured data provider server. The computer device 220 and the mobile device 230 can also store information warranting security measures, such as personal bank records, medical information, and login information, e.g., login information to a server 216 of the enterprise 200, or to some other secured data provider server.

Example Processing Node Architecture

In an embodiment, the processing nodes 110 are external to network edges of the external systems 200, 220 and 230. Each of the processing nodes 110 stores security policy data 113 received from the authority node 120 and monitors content items requested by or sent from the external systems 200, 220 and 230. In an embodiment, each of the processing nodes 110 may also store a detection process filter 112 and/or threat data 114 to facilitate the decision of whether a content item should be processed for threat detection. A processing node manager 118 may manage each content item in accordance with the security policy data 113, and the detection process filter 112 and/or threat data 114, if stored at the processing node 110, so that security policies for a plurality of external systems in data communication with the processing node 110 are implemented external to the network edges for each of the external systems 200, 220 and 230. For example, depending on the classification resulting from the monitoring, the content item may be allowed, precluded, or threat detected. In general, content items that are already classified as “clean” or not posing a threat can be allowed, while those classified as “violating” may be precluded. Those content items having an unknown status, e.g., content items that have not been processed by the system 100, may be threat detected to classify the content item according to threat classifications.

The processing node 110 may include a state manager 116A. The state manager 116A may be used to maintain the authentication and the authorization states of users that submit requests to the processing node 110. Maintenance of the states through the state manager 116A may minimize the number of authentication and authorization transactions that are necessary to process a request. The processing node 110 may also include an epoch processor 116B. The epoch processor 116B may be used to analyze authentication data that originated at the authority node 120. The epoch processor 116B may use an epoch ID to validate further the authenticity of authentication data. The processing node 110 may further include a source processor 116C. The source processor 116C may be used to verify the source of authorization and authentication data. The source processor 116C may identify improperly obtained authorization and authentication data, enhancing the security of the network. Collectively, the state manager 116A, the epoch processor 116B, and the source processor 116C operate as data inspection engines.

Because the amount of data being processed by the processing nodes 110 may be substantial, the detection processing filter 112 may be used as the first stage of an information lookup procedure. For example, the detection processing filter 112 may be used as a front-end to a looking of the threat data 114. Content items may be mapped to index values of the detection processing filter 112 by a hash function that operates on an information key derived from the information item. The information key is hashed to generate an index value (i.e., a bit position). A value of zero in a bit position in the guard table can indicate, for example, the absence of information, while a one in that bit position can indicate the presence of information. Alternatively, a one could be used to represent absence, and a zero to represent presence. Each content item may have an information key that is hashed. For example, the processing node manager 118 may identify the Uniform Resource Locator (URL) address of URL requests as the information key and hash the URL address; or may identify the file name and the file size of an executable file information key and hash the file name and file size of the executable file. Hashing an information key to generate an index and checking a bit value at the index in the detection processing filter 112 generally requires less processing time than actually searching threat data 114. The use of the detection processing filter 112 may improve the failure query (i.e., responding to a request for absent information) performance of database queries and/or any general information queries. Because data structures are generally optimized to access information that is present in the structures, failure query performance has a greater effect on the time required to process information searches for very rarely occurring items, e.g., the presence of file information in a virus scan log or a cache where many or most of the files transferred in a network have not been scanned or cached. Using the detection processing filter 112, however, the worst case additional cost is only on the order of one, and thus its use for most failure queries saves on the order of m log m, where m is the number of information records present in the threat data 114.

The detection processing filter 112 thus improves the performance of queries where the answer to a request for information is usually positive. Such instances may include, for example, whether a given file has been virus scanned, whether content at a given URL has been scanned for inappropriate (e.g., pornographic) content, whether a given fingerprint matches any of a set of stored documents, and whether a checksum corresponds to any of a set of stored documents. Thus, if the detection processing filter 112 indicates that the content item has not been processed, then a worst case null lookup operation into the threat data 114 is avoided, and a threat detection can be implemented immediately. The detection processing filter 112 thus complements the threat data 114 that capture positive information. In an embodiment, the detection processing filter 112 may be a Bloom filter implemented by a single hash function. The Bloom filter may be sparse table, i.e., the tables include many zeros and few ones, and the hash function is chosen to minimize or eliminate false negatives which are, for example, instances where an information key is hashed to a bit position, and that bit position indicates that the requested information is absent when it is actually present.

Example Authority Node Architecture

In general, the authority node 120 includes a data store that stores master security policy data 123 for each of the external systems 200, 220 and 230. An authority node manager 128 may be used to manage the master security policy data 123, e.g., receive input from users of each of the external systems defining different security policies, and may distribute the master security policy data 123 to each of the processing nodes 110. The processing nodes 110 then store a local copy of the security policy data 113. The authority node 120 may also store a master detection process filter 122. The detection processing filter 122 may include data indicating whether content items have been processed by one or more of the data inspection engines 116 in any of the processing nodes 110. The authority node manager 128 may be used to manage the master detection processing filter 122, e.g., receive updates from a processing node 110 when the processing node 110 has processed a content item and update the master detection processing filter 122. For example, the master detection processing filter 122 may be distributed to the processing nodes 110, which then store a local copy of the detection processing filter 112.

In an embodiment, the authority node 120 may include an epoch manager 126. The epoch manager 126 may be used to generate authentication data associated with an epoch ID. The epoch ID of the authentication data is a verifiable attribute of the authentication data that can be used to identify fraudulently created authentication data. In an embodiment, the detection processing filter 122 may be a guard table. The processing node 110 may, for example, use the information in the local detection processing filter 112 to quickly determine the presence and/or absence of information, e.g., whether a particular URL has been checked for malware; whether a particular executable has been virus scanned, etc. The authority node 120 may also store master threat data 124. The master threat data 124 may classify content items by threat classifications, e.g., a list of known viruses, a list of known malware sites, spam email domains, list of known or detected phishing sites, etc. The authority node manager 128 may be used to manage the master threat data 124, e.g., receive updates from the processing nodes 110 when one of the processing nodes 110 has processed a content item and update the master threat data 124 with any pertinent results. In some implementations, the master threat data 124 may be distributed to the processing nodes 110, which then store a local copy of the threat data 114. In another embodiment, the authority node 120 may also monitor the health of each of the processing nodes 110, e.g., the resource availability in each of the processing nodes 110, detection of link failures, etc. Based on the observed health of each of the processing nodes 110, the authority node 120 may redirect traffic among the processing nodes 110 and/or balance traffic among the processing nodes 110. Other remedial actions and processes may also be facilitated by the authority node 120.

Example Processing Node and Authority Node Communications

The processing node 110 and the authority node 120 may be configured according to one or more push and pull processes to manage content items according to security policy data 113 and/or 123, detection process filters 112 and/or 122, and the threat data 114 and/or 124. In a threat data push implementation, each of the processing nodes 110 stores policy data 113 and threat data 114. The processing node manager 118 determines whether a content item requested by or transmitted from an external system is classified by the threat data 114. If the content item is determined to be classified by the threat data 114, then the processing node manager 118 may manage the content item according to the security classification of the content item and the security policy of the external system. If, however, the content item is determined not to be classified by the threat data 114, then the processing node manager 118 may cause one or more of the data inspection engines 117 to perform the threat detection processes to classify the content item according to a threat classification. Once the content item is classified, the processing node manager 118 generates a threat data update that includes data indicating the threat classification for the content item from the threat detection process and transmits the threat data update to an authority node 120.

The authority node manager 128, in response to receiving the threat data update, updates the master threat data 124 stored in the authority node data store according to the threat data update received from the processing node 110. In an embodiment, the authority node manager 128 may automatically transmit the updated threat data to the other processing nodes 110. Accordingly, threat data for new threats as the new threats are encountered are automatically distributed to each processing node 110. Upon receiving the new threat data from the authority node 120, each of processing node managers 118 may store the updated threat data in the locally stored threat data 114.

In a threat data pull and push implementation, each of the processing nodes 110 stores policy data 113 and threat data 114. The processing node manager 118 determines whether a content item requested by or transmitted from an external system is classified by the threat data 114. If the content item is determined to be classified by the threat data 114, then the processing node manager 118 may manage the content item according to the security classification of the content item and the security policy of the external system. If, however, the content item is determined not to be classified by the threat data, then the processing node manager 118 may request responsive threat data for the content item from the authority node 120. Because processing a content item may consume valuable resource and time, in some implementations the processing node 110 may first check with the authority node 120 for threat data 114 before committing such processing resources.

The authority node manager 128 may receive the responsive threat data request from the processing node 110 and may determine if the responsive threat data is stored in the authority node data store. If responsive threat data is stored in the master threat data 124, then the authority node manager 128 provide a reply that includes the responsive threat data to the processing node 110 so that the processing node manager 118 may manage the content item in accordance with the security policy data 113 and the classification of the content item. Conversely, if the authority node manager 128 determines that responsive threat data is not stored in the master threat data 124, then the authority node manager 128 may provide a reply that does not include the responsive threat data to the processing node 110. In response, the processing node manager 118 can cause one or more of the data inspection engines 116 to perform the threat detection processes to classify the content item according to a threat classification. Once the content item is classified, the processing node manager 118 generates a threat data update that includes data indicating the threat classification for the content item from the threat detection process and transmits the threat data update to an authority node 120. The authority node manager 128 can then update the master threat data 124. Thereafter, any future requests related to responsive threat data for the content item from other processing nodes 110 can be readily served with responsive threat data.

In a detection process filter and threat data push implementation, each of the processing nodes 110 stores a detection process filter 112, policy data 113, and threat data 114. The processing node manager 118 accesses the detection process filter 112 to determine whether the content item has been processed. If the processing node manager 118 determines that the content item has been processed, it may determine if the content item is classified by the threat data 114. Because the detection process filter 112 has the potential for a false positive, a lookup in the threat data 114 may be implemented to ensure that a false positive has not occurred. The initial check of the detection process filter 112, however, may eliminate many null queries to the threat data 114, which, in turn, conserves system resources and increases efficiency. If the content item is classified by the threat data 114, then the processing node manager 118 may manage the content item in accordance with the security policy data 113 and the classification of the content item. Conversely, if the processing node manager 118 determines that the content item is not classified by the threat data 114, or if the processing node manager 118 initially determines through the detection process filter 112 that the content item is not classified by the threat data 114, then the processing node manager 118 may cause one or more of the data inspection engines 116 to perform the threat detection processes to classify the content item according to a threat classification. Once the content item is classified, the processing node manager 118 generates a threat data update that includes data indicating the threat classification for the content item from the threat detection process and transmits the threat data update to one of the authority nodes 120.

The authority node manager 128, in turn, may update the master threat data 124 and the master detection process filter 122 stored in the authority node data store according to the threat data update received from the processing node 110. In an embodiment, the authority node manager 128 may automatically transmit the updated threat data and detection processing filter to other processing nodes 110. Accordingly, threat data and the detection processing filter for new threats as the new threats are encountered and automatically distributed to each processing node 110, and each processing node 110 may update its local copy of the detection processing filter 112 and threat data 114.

In a detection process filter and threat data pull and push implementation, each of the processing nodes 110 stores a detection process filter 112, policy data 113, and threat data 114. The processing node manager 118 accesses the detection process filter 112 to determine whether the content item has been processed. If the processing node manager 118 determines that the content item has been processed, it may determine if the content item is classified by the threat data 114. Because the detection process filter 112 has the potential for a false positive, a lookup in the threat data 114 can be implemented to ensure that a false positive has not occurred. The initial check of the detection process filter 112, however, may eliminate many null queries to the threat data 114, which, in turn, conserves system resources and increases efficiency. If the processing node manager 118 determines that the content item has not been processed, it may request responsive threat data for the content item from the authority node 120. Because processing a content item may consume valuable resource and time, in some implementations the processing node 110 may first check with the authority node 120 for threat data 114 before committing such processing resources.

The authority node manager 128 may receive the responsive threat data request from the processing node 110 and may determine if the responsive threat data is stored in the authority node data 120 store. If responsive threat data is stored in the master threat data 124, then the authority node manager 128 provides a reply that includes the responsive threat data to the processing node 110 so that the processing node manager 118 can manage the content item in accordance with the security policy data 113 and the classification of the content item, and further update the local detection processing filter 112. Conversely, if the authority node manager 128 determines that responsive threat data is not stored in the master threat data 124, then the authority node manager 128 may provide a reply that does not include the responsive threat data to the processing node 110. In response, the processing node manager 118 may cause one or more of the data inspection engines 116 to perform the threat detection processes to classify the content item according to a threat classification. Once the content item is classified, the processing node manager 118 generates a threat data update that includes data indicating the threat classification for the content item from the threat detection process and transmits the threat data update to an authority node 120. The authority node manager 128 may then update the master threat data 124. Thereafter, any future requests for related to responsive threat data for the content item from other processing nodes 110 can be readily served with responsive threat data.

The various push and pull data exchange processes provided above are example processes for which the threat data and/or detection process filters may be updated in the system 100 of FIGS. 1 and 2. Other update processes, however, are contemplated with the present invention. The data inspection engines 116, processing node manager 118, authority node manager 128, user interface manager 132, logging node manager 148, and authority agent 180 may be realized by instructions that upon execution cause one or more processing devices to carry out the processes and functions described above. Such instructions can, for example, include interpreted instructions, such as script instructions, e.g., JavaScript or ECMAScript instructions, or executable code, or other instructions stored in a non-transitory computer readable medium. Other processing architectures can also be used, e.g., a combination of specially designed hardware and software, for example.

Example Server Architecture

FIG. 3 is a block diagram of a server 300 which may be used in the system 100, in other systems, or standalone. Any of the processing nodes 110, the authority nodes 120, and the logging nodes 140 may be formed through one or more servers 300. Further, the computer device 220, the mobile device 230, the servers 216, etc. may include the server 300 or a similar structure. The server 300 may be a digital computer that, in terms of hardware architecture, generally includes a processor 302, input/output (I/O) interfaces 304, a network interface 306, a data store 308, and memory 310. It should be appreciated by those of ordinary skill in the art that FIG. 3 depicts the server 300 in an oversimplified manner, and a practical embodiment may include additional components and suitably configured processing logic to support known or conventional operating features that are not described in detail herein. The components (302, 304, 306, 308, and 310) are communicatively coupled via a local interface 312. The local interface 312 may be, for example, but not limited to, one or more buses or other wired or wireless connections, as is known in the art. The local interface 312 may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers, among many others, to enable communications. Further, the local interface 312 may include address, control, and/or data connections to enable appropriate communications among the aforementioned components.

The processor 302 is a hardware device for executing software instructions. The processor 302 may be any custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the server 300, a semiconductor-based microprocessor (in the form of a microchip or chip set), or generally any device for executing software instructions. When the server 300 is in operation, the processor 302 is configured to execute software stored within the memory 310, to communicate data to and from the memory 310, and to generally control operations of the server 300 pursuant to the software instructions. The I/O interfaces 304 may be used to receive user input from and/or for providing system output to one or more devices or components. User input may be provided via, for example, a keyboard, touchpad, and/or a mouse. System output may be provided via a display device and a printer (not shown). I/O interfaces 304 may include, for example, a serial port, a parallel port, a small computer system interface (SCSI), a serial ATA (SATA), a fibre channel, Infiniband, iSCSI, a PCI Express interface (PCI-x), an infrared (IR) interface, a radio frequency (RF) interface, and/or a universal serial bus (USB) interface.

The network interface 306 may be used to enable the server 300 to communicate over a network, such as the Internet, the WAN 101, the enterprise 200, and the like, etc. The network interface 306 may include, for example, an Ethernet card or adapter (e.g., 10BaseT, Fast Ethernet, Gigabit Ethernet, 10 GbE) or a wireless local area network (WLAN) card or adapter (e.g., 802.11a/b/g/n). The network interface 306 may include address, control, and/or data connections to enable appropriate communications on the network. A data store 308 may be used to store data. The data store 308 may include any of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, and the like)), nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, and the like), and combinations thereof. Moreover, the data store 308 may incorporate electronic, magnetic, optical, and/or other types of storage media. In one example, the data store 308 may be located internal to the server 300 such as, for example, an internal hard drive connected to the local interface 312 in the server 300. Additionally, in another embodiment, the data store 308 may be located external to the server 300 such as, for example, an external hard drive connected to the I/O interfaces 304 (e.g., SCSI or USB connection). In a further embodiment, the data store 308 may be connected to the server 300 through a network, such as, for example, a network attached file server.

The memory 310 may include any of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)), nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, etc.), and combinations thereof. Moreover, the memory 310 may incorporate electronic, magnetic, optical, and/or other types of storage media. Note that the memory 310 may have a distributed architecture, where various components are situated remotely from one another but can be accessed by the processor 302. The software in memory 310 may include one or more software programs, each of which includes an ordered listing of executable instructions for implementing logical functions. The software in the memory 310 includes a suitable operating system (O/S) 314 and one or more programs 316. The operating system 314 essentially controls the execution of other computer programs, such as the one or more programs 316, and provides scheduling, input-output control, file and data management, memory management, and communication control and related services. The one or more programs 316 may be configured to implement the various processes, algorithms, methods, techniques, etc. described herein.

Example Mobile Device Architecture

FIG. 4 is a block diagram of a mobile device 400, which may be used in the system 100 or the like. The mobile device 400 can be a digital device that, in terms of hardware architecture, generally includes a processor 402, input/output (I/O) interfaces 404, a radio 406, a data store 408, and memory 410. It should be appreciated by those of ordinary skill in the art that FIG. 4 depicts the mobile device 400 in an oversimplified manner, and a practical embodiment may include additional components and suitably configured processing logic to support known or conventional operating features that are not described in detail herein. The components (402, 404, 406, 408, and 402) are communicatively coupled via a local interface 412. The local interface 412 can be, for example, but not limited to, one or more buses or other wired or wireless connections, as is known in the art. The local interface 412 can have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers, among many others, to enable communications. Further, the local interface 412 may include address, control, and/or data connections to enable appropriate communications among the aforementioned components.

The processor 402 is a hardware device for executing software instructions. The processor 402 can be any custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the mobile device 400, a semiconductor-based microprocessor (in the form of a microchip or chip set), or generally any device for executing software instructions. When the mobile device 400 is in operation, the processor 402 is configured to execute software stored within the memory 410, to communicate data to and from the memory 410, and to generally control operations of the mobile device 400 pursuant to the software instructions. In an embodiment, the processor 402 may include an optimized mobile processor such as optimized for power consumption and mobile applications. The I/O interfaces 404 can be used to receive user input from and/or for providing system output. User input can be provided via, for example, a keypad, a touch screen, a scroll ball, a scroll bar, buttons, barcode scanner, and the like. System output can be provided via a display device such as a liquid crystal display (LCD), touch screen, and the like. The I/O interfaces 404 can also include, for example, a serial port, a parallel port, a small computer system interface (SCSI), an infrared (IR) interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, and the like. The I/O interfaces 404 can include a graphical user interface (GUI) that enables a user to interact with the mobile device 400. Additionally, the I/O interfaces 404 may further include an imaging device, i.e., camera, video camera, etc.

The radio 406 enables wireless communication to an external access device or network. Any number of suitable wireless data communication protocols, techniques, or methodologies can be supported by the radio 406, including, without limitation: RF; IrDA (infrared); Bluetooth; ZigBee (and other variants of the IEEE 802.15 protocol); IEEE 802.11 (any variation); IEEE 802.16 (WiMAX or any other variation); Direct Sequence Spread Spectrum; Frequency Hopping Spread Spectrum; Long Term Evolution (LTE); cellular/wireless/cordless telecommunication protocols (e.g. 3G/4G, etc.); wireless home network communication protocols; paging network protocols; magnetic induction; satellite data communication protocols; wireless hospital or health care facility network protocols such as those operating in the WMTS bands; GPRS; proprietary wireless data communication protocols such as variants of Wireless USB; and any other protocols for wireless communication. The data store 408 may be used to store data. The data store 408 may include any of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, and the like)), nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, and the like), and combinations thereof. Moreover, the data store 408 may incorporate electronic, magnetic, optical, and/or other types of storage media.

The memory 410 may include any of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)), nonvolatile memory elements (e.g., ROM, hard drive, etc.), and combinations thereof. Moreover, the memory 410 may incorporate electronic, magnetic, optical, and/or other types of storage media. Note that the memory 410 may have a distributed architecture, where various components are situated remotely from one another but can be accessed by the processor 402. The software in memory 410 can include one or more software programs, each of which includes an ordered listing of executable instructions for implementing logical functions. In the example of FIG. 4, the software in the memory 410 includes a suitable operating system (O/S) 414 and programs 416. The operating system 414 essentially controls the execution of other computer programs and provides scheduling, input-output control, file and data management, memory management, and communication control and related services. The programs 416 may include various applications, add-ons, etc. configured to provide end user functionality with the mobile device 400. For example, example programs 416 may include, but not limited to, a web browser, social networking applications, streaming media applications, games, mapping and location applications, electronic mail applications, financial applications, and the like. In a typical example, the end user typically uses one or more of the programs 416 along with a network such as the system 100.

Example General Cloud System

FIG. 5 is a diagram of a cloud system 500 is illustrated for implementing the systems and methods described herein for tracking and auditing changes in a multi-tenant cloud system. The cloud system 500 includes one or more cloud nodes (CN) 502 communicatively coupled to the Internet 504. The cloud nodes 502 may include the processing nodes 110, the server 300, or the like. That is, the cloud system 500 may include the distributed security system 100 or another implementation of a cloud0based system, such as a system providing different functionality from security. In the cloud system 500, traffic from various locations (and various devices located therein) such as a regional office 510, headquarters 520, various employee's homes 530, mobile laptop 540, and mobile device 542 communicates to the cloud through the cloud nodes 502. That is; each of the locations 510, 520, 530, 540, 542 is communicatively coupled to the Internet 504 through the cloud nodes 502. For security, the cloud system 500 may be configured to perform various functions such as spam filtering, uniform resource locator (URL) filtering, antivirus protection, bandwidth control, data loss prevention, zero-day vulnerability protection, web 2.0 features, and the like. In an embodiment, the cloud system 500 and the distributed security system 100 may be viewed as Security-as-a-Service through the cloud. In general, the cloud system 500 can be configured to perform any function in a multi-tenant environment. For example, the cloud system 500 can provide content, a collaboration between users, storage, application hosting, and the like.

In an embodiment, the cloud system 500 can utilize the systems and methods for tracking and auditing changes in a multi-tenant cloud system. That is, the cloud system 500 can track and audit administrator activity associated with the cloud system 500 in a segregated and overlaid fashion from the application functions performed by the cloud system 500. This segregated and overlaid fashion decouples the tracking and auditing from application logic, maximizing resources and minimizing development complexity and runtime processing. The cloud system 500 (and the system 100) can be offloaded from complex tracking and auditing functions so that it can provide its primary function. In the context of a distributed security system, the tracking and auditing systems and methods enable accountability, intrusion detection, problem diagnosis, and data reconstruction, all in an optimized fashion considering the exponential growth in cloud-based systems.

DNS Augmented Security

In an embodiment, the cloud system 500 and/or the distributed security system 100 can be used to perform DNS surrogation. Specifically, DNS surrogation can be a framework for distributed or cloud-based security/monitoring as is described herein. Endpoint security is no longer effective as deployments move to the cloud with users accessing content from a plurality of devices in an anytime, anywhere connected manner. As such, cloud-based security is the most effective means to ensure network protection where different devices are used to access network resources. Traffic inspection in the distributed security system 100 and the cloud-based system 500 is performed in an in-line manner, i.e., the processing nodes 110 and the cloud nodes 502 are in the data path of connecting users. Another approach can include a passive approach to the data path. DNS is one of the most fundamental IP protocols. With DNS surrogation as a technique, it is proposed to use DNS for dynamic routing of traffic, per user authentication and policy enforcement, and the like.

In conjunction with the cloud system 500 and/or the distributed security system 100, various techniques can be used for monitoring which are described on a sliding scale between always inline to never inline. First, in an always inline manner, all user traffic is between inline proxies such as the processing nodes 110 or the cloud nodes 502 without exception. Here, DNS can be used as a forwarding mechanism to the inline proxies. Second, in a somewhat always inline manner, all user traffic except for certain business partners or third parties is between inline proxies such as the processing nodes 110 or the cloud nodes 502. Third, in an inline manner for most traffic, high bandwidth applications can be configured to bypass the inline proxies such as the processing nodes 110 or the cloud nodes 502. Example high bandwidth applications can include content streaming such as video (e.g., Netflix, Hulu, YouTube, etc.) or audio (e.g., Pandora, etc.). Fourth, in a mixed manner, inline monitoring can be used for “interesting” traffic as determined by security policy with other traffic being direct. Fifth, in an almost never inline manner, simple domain-level URL filtering can be used to determine what is monitored inline. Finally, sixth, in a never inline manner, DNS augmented security can be used.

FIG. 6 is a network diagram of a network 550 with a distributed security cloud 552 providing DNS augmented security. The network 550 includes a user device 554 connecting to the distributed security cloud 552 via an anycast DNS server 556. The anycast DNS server 556 can be a server such as the server 300 of FIG. 3. Also, the anycast DNS server 556 can be the processing node 110, the cloud node 502, etc. The distributed security cloud 552 includes the anycast DNS server 556, policy data 558, and an inline proxy 560. The inline proxy 560 can include the processing node 110, the cloud node 502, etc. In operation, the user device 554 is configured with a DNS entry of the anycast DNS server 556, and the anycast DNS server 556 can perform DNS surrogation as is described herein. The distributed security cloud 552 utilizes the anycast DNS server 556, the policy data 558, and the inline proxy 560 to perform the DNS augmented security.

The network 550 illustrates the DNS augmented security where DNS information is used as follows. First, at step 562, the user device 554 requests a DNS lookup of a site, e.g., “what is the IP address of site.com?” from the anycast DNS server 556. The anycast DNS server 556 accesses the policy data 558 to determine the policy associated with the site at step 564. The anycast DNS server 556 returns the IP address of the site based on the appropriate policy at step 566. The policy data 558 determines if the site either goes direct (step 568) to the Internet, is inspected by the inline proxy (step 570), or is blocked per policy (step 572). Here, the anycast DNS server 556 returns the IP address with additional information if the site is inspected or blocked. For example, if the anycast DNS server 556 determines the access is direct, the anycast DNS server 556 simply returns the IP address of the site. If the anycast DNS server 556 determines the site is blocked or inspected, the anycast DNS server 556 returns the IP address to the inline proxy 560 with additional information. The inline proxy 560 can block the site or provide fully in line proxied traffic to the site (step 574) after performing monitoring for security.

The DNS augmented security advantageously is protocol and application agnostic providing visibility and control across virtually all Internet-bound traffic. For example, DNS-based protocols include Internet Relay Chat (IRC), Session Initiation Protocol (SIP), Hypertext Transfer Protocol (HTTP), HTTP Secure (HTTPS), Post Office Protocol v3 (POP3), Internet Message Access Protocol (IMAP), etc. Further, emerging threats are utilizing DNS today especially Botnets and advanced persistent threats (APTs). For example, Fast flux is a DNS technique used to hide phishing and malware delivery sites behind an ever-changing network of compromised hosts acting as proxies. The DNS augmented security provides deployment flexibility when full inline monitoring is not feasible. For example, this can be utilized in highly distributed with high bandwidth environments, in locations with challenging Internet Access, etc. The DNS augmented security can provide URL filtering, white/black list enforcement, etc. for enhanced security without content filtering. In this manner, the network 550 can be used with the distributed security system 100 and the cloud system 500 to provide cloud-based security without requiring full inline connectivity.

Unified Agent Application

FIG. 7 is a network diagram of a unified agent application 600 and associated connectivity and functionality in a network 602. The unified agent application 600 is executed on a mobile device 604. The unified agent application 600 dynamically learns all available services, adapts to changing network environments, and provides a seamless and a secure network resource access to Internet and darknet hosted applications. This is achieved through dynamic evaluation of network conditions, enrollment to individual services, learning individual service protocols, creating a link-local network on the device 604, and establishing multiple secure tunnels to cloud services over this local network.

The unified agent application 600 is communicatively coupled to an agent manager cloud 606, and a security cloud 608. Note, the security cloud 608 can be the distributed security system 100, the cloud system 500, the distributed security cloud 552, etc. The unified agent application 600 enables communication to enterprise private resources 612 via the security cloud 608 and to the Internet 504 via the security cloud 608. The agent manager cloud 606 can communicate with enterprise asset management 614, an enterprise Security Assertion Markup Language (SAML) Identity provider (IDP) 616, and an enterprise Certificate Authority (CA) 618. The device 604 and the unified agent application 600 can perform a registration/identity 620 process through the agent manager cloud 606 where the user identity, the user's certificates, and a device fingerprint can uniquely identify the device 604. Once registered, the unified agent application 600 has an identity 622 which can include the user, certificates, device posture, etc. and which is shared with the security cloud 608.

The unified agent application 600 operates on a client-server model where an IT admin enables appropriate services for end users at a Cloud Administration Server (CAS) which can be part of an agent manager cloud 606, namely the enterprise asset management 614. Every client can make a unicast request to the agent manager cloud 606 (e.g., CAS) to discover all enabled services. On acknowledging the response, the client issues a request to authenticate to each service's cloud Identity Providers, the enterprise SAML IDP 616. Authentication can be multi-factor depending upon the nature of the service. On successful authentication, server contacts Mobile Device Management (MDM) or Inventory management provider to define access control rights for the device 604. Post authorization, the device 604 is successfully enrolled into the agent manager cloud 606 which tracks and monitors all behavior of the device 604.

Post-enrollment, the device 604 creates a link local network with a specific IP configuration, opens a virtual network interface to read and write packets and opens multiple listening sockets at custom ports to create secure tunnels to available services through the security cloud 608. On network changes, the device 604 dynamically evaluates reachability to preconfigured domains and depending upon the result it appropriately transitions all network tunnels, thus providing a seamless experience to the end user. Further, the device 604 also intelligently learns the conditions which are appropriate for setting up network tunnels to cloud services depending upon several network heuristics such as reachability to a particular cloud service.

Unified Agent Application—Functionality

Generally, the unified agent application 600 support two broad functional categories—1) dynamic service discovery and access controls and 2) service availability. The dynamic service discovery and access controls include service configuration by the administrator, service discovery by the device 604, service acknowledgment and authentication, service authorization and enrollment, and the like. For service configuration by the administrator, the IT admin can provide cloud service details at a centralized knowledge server, such as part of the agent manager cloud 606, the enterprise asset management 614, etc. The cloud service details include the service type (e.g., Internet/intranet), network protocol, identity provider, server address, port and access controls, etc.

For service discovery by the device 604, the device 604 can issue a network request to a known Cloud Administrative Server (CAS) in the agent manager cloud 606 to discover all enabled services for a user. If a specific cloud server is not known a priori, the device 604 can broadcast the request to multiple clouds, e.g., through the agent manager cloud 606 communicating to the enterprise asset management 614, the enterprise SAML IDP 616, and the enterprise CA 618.

For the service acknowledgment and authentication, the device 604 acknowledges the response of service discovery and initiates the authentication flow. The device 604 learns the authentication protocol through the service discovery configuration and performs authentication of a configured nature at the enterprise SAML IDP 616. For the service authorization and enrollment, post successful authentication, the CAS, authorizes the device 604 and fetches the access control information by contacting a MDM/Inventory Solutions Provider. Depending upon the user context and the nature of access, the CAS enrolls the device 604 into several cloud services and informs the cloud services that the user has been enrolled for access.

The service availability includes link local network setup, a traffic interceptor, and dynamic traffic forwarding tunnels to authorized services. The link local network setup, post enrollment, has the device 604 create a local network on the device 604 itself to manage various networking functionalities. For the traffic interceptor, the device 604 intercepts and evaluates all Internet traffic. Allowed traffic is tunneled to the cloud services such as in the security cloud 608 whereas rest of the traffic is denied as per enterprise policies. For the dynamic traffic forwarding tunnels to authorized services, depending upon the evaluation, the device 604 splits the traffic into the different tunnel to individual cloud services such as in the security cloud 608.

The unified agent application 600 is a single application that provides security connectivity to the Internet 504 and darknet hosted applications, such as the enterprise private resources 612. The unified agent application 600 communicates securely to the agent manager 606 which is controlled by an IT admin. The unified agent application 600 learns available services and authenticates with each service. Post proper enrollment, the unified agent application 600 securely connects to cloud services by means of network tunnels.

Unified Agent Application—Workflow

FIG. 8 is a network diagram of the workflow of the unified agent application 600 in the network 602. The device 604 again executes the unified agent application 600, as well as a browser 630 (or some other application requesting network services). FIG. 8 illustrates example workflow. First, the device 604 includes authentication through an application portal 632 and download/install of the unified agent application 600 therefrom (step 640-1). Note, the application portal 632 can be a website, Apple's app store, Google Play, Windows Store, etc. Once installed, the unified agent application 600 communicates to the agent manager cloud 606 communicating identity and asking for available services (“I am User X, what are my services?”) and the agent manager cloud 606 responds with the available services (“You have Z services”) (step 640-2).

Next, the unified agent application 600 includes authentication using a VPN Service Provider (SP) with the security cloud 608 (step 640-3). The unified agent application 600 next enrolls the device 604 through the agent manager cloud 606 (step 640-4). The agent manager cloud 606 performs a device asset policy check with the enterprise asset management 614 (step 640-5). The agent manager cloud 606, upon successful check, provides the unified agent application 600 an affirmative response (step 640-6). The unified agent application 600 sends a Certificate Signing Request (CSR) to the agent manager cloud 606 (step 640-7), and the agent manager cloud 606 sends the CSR request to the enterprise CA, and the certificate is returned to the unified agent application 600 (step 640-8). Finally, the unified agent application 600 enables VPN connectivity to the security cloud 608 (step 640-9).

FIG. 9 is a flow diagram of an event sequence associated with the unified agent application 600 in the network 602. The event sequence is shown between the device 604 executing the unified agent application 600, a mobile admin function 650 such as implemented through the agent manager cloud 606, a cloud node 502, a VPN node 652 such as through the security cloud 608, a MDM function 654 such as through the enterprise asset management 614, and an IDP function 656 such as through the enterprise SAML IDP 616. The device 604 discovers services with the mobile admin function 650 (step 660), and the device 604 is authenticated by the IDP function 656 (step 662). The device 604 enrolls in discovered services through the mobile admin function 650 (step 664).

The mobile admin function 650 is configured to authorize the services with the MDM function 654 (step 666), enroll in the services through the VPN node 652 (step 668) and the processing nodes 110/cloud nodes 502 (step 670). A success/error is provided by the mobile admin function 650 to the device 604. Subsequently, the device 604, through the unified agent application 600, accesses the services such as a secure tunnel for internet access through the processing nodes 110/cloud nodes 502 (step 674) or a secure tunnel for intranet access through the VPN node 652 (step 676).

Unified Agent Application—Architecture

FIG. 10 is a logical diagram of functional components of the unified agent application 600. The unified agent application 600 is configured to operate on the mobile device 604. The security cloud 608, e.g., through the distributed security system 100 or the cloud system 500, provides Internet security as well as cloud-based remote access to enterprise internal resources, through a VPN. These cloud services are designed and well suited for road warriors. Road warriors are the users who are accessing Internet and enterprise internal services from outside the corporate physical network perimeter, i.e., the mobile laptop 540 and/or the mobile device 542 in the cloud system 500. These are the users who are accessing Internet and Enterprise resources from home, airports, coffee shops, and other external unsecured hotspots.

The unified agent application 600 provides authenticated and encrypted tunnels from road warrior devices 604 and, in some use cases, it even needs to be enforceable so that end users cannot disable the unified agent application 600. The VPN, which is the remote access service, also needs authenticated and encrypted tunnel from road warrior devices 604. Both of these solutions also need to provide feedback to the end user in the event that access was blocked due to security or compliance reasons. The following describes the architecture and design of the unified agent application 600 including an endpoint client architecture, backend changes, auto update and integration with the security cloud 608.

The unified agent application 600 includes logical components including view components 702, business processes and services 704, data 706, and cross-cutting functions 708. The view components 702 include User Interface (UI) components 710 and UI process components 712. The business processes and services 704 include a tray user process 714, a helper user process 716, a tunnel system service 718, a posture system service 720, and an updater system service 722. The data 706 includes encrypted data 724, configuration data 726, and logs 728. The cross-cutting functions 708 are across the view components 702, the business processes and services 704, and the data 706 and include security 730, logging 732, and statistics 734.

The unified agent application 600 has a use goal of simplified provisioning of the proxy (for security through the security cloud 608 to the Internet 504) and the VPN (for access through the security cloud 608 to the enterprise private resources 612). That is, the unified agent application 600 allows the use of the distributed security system 100, the cloud system 500, the distributed security cloud 552, the security cloud 608, etc. as a proxy for Internet-bound communications. The unified agent application 600 further allows the use of the distributed security system 100, the cloud system 500, the distributed security cloud 552, the security cloud 608, etc. as a tunnel for Intranet-bound communications to the enterprise private resources 412. With the unified agent application 600 setting up a local network at the device 604, the unified agent application 600 can manage communications between the Internet and the Intranet, i.e., two of the main categories of cloud services—proxy to the Internet and tunnel to the Intranet. The unified agent application 600 further has objectives of simplified user enrollment in the proxy and tunnels.

In an embodiment, the unified agent application 600 is a native application. The common functionality is abstracted out and made into common libraries based on C or C++ so that it can be reused across different platforms (e.g., iOS, Android, etc.). Example functionality: Traffic forwarding tunnels, local proxy, authentication backend, logging, statistics, etc. The UI components 710 and UI process components 712 can be platform dependent. Also, the unified agent application 600 is designed and implementable such that other third party VPN applications, if configured by the enterprise, can be used concurrently.

The app portal 632 enables installation of the unified agent application 600 on the device 604. For example, an admin may be able to push and install the unified agent application 600 to the device 604 using remote-push mechanisms like GPO, MDMs, etc. Additionally, the user can download the unified agent application 600 if they have access to installation file and install on their own. The unified agent application 600 supports automatic updates without impacting the user's Internet experience. If a problem is encountered, then it should roll back to previously successful state or fail open. The unified agent application 600 can have a security check to ensure that it is not tampered and updated from a right source with a hash match with a source hash when upgrading.

The user is able to log into the unified agent application 600 such as with a User ID and password, as illustrated in FIG. 11. Once the user sends their User ID through the unified agent application 600 to the agent manager cloud 606, the security cloud 608, and/or the app portal 632, the app portal 632 can determine the company's authentication mechanism, such as through a lookup in the enterprise asset management 614, and validate password through the enterprise CA 618.

Through the unified agent application 600, a user can be authenticated to the proxy or the VPN through the security cloud 608. For authentication of the user to the proxy, using SAML, the user is able to log into the unified agent application 600 by using their user ID and transparent SAML authentication thereafter, including SAML certificate. The app portal 632 shall determine that an organization is using SAML for authentication through the enterprise CA 618 and redirect to the enterprise SAML IDP 616 to get SAML assertion and use it to authenticate the user.

For authentication of the user to the tunnel, using SAML, the user is able to log into the unified agent application 600 by just using their user ID and based on the user ID, the unified agent application 600 shall redirect the user for authentication to enterprise SAML IDP 616 and SAML assertion shall be sent. The VPN service shall validate SAML assertion; if the assertion is valid, then the unified agent application 600 shall collect hardware parameters like device serial number, model number, etc. and create CSR. The CSR shall be signed by the enterprise CA 618, and the certificate shall be pushed to the unified agent application 600. The unified agent application 600 shall install the certificate to KMS/keychain and save assertion.

After the user has been successfully authenticated, the user shall be enrolled in the proxy service, and user's traffic forwarding profile shall be downloaded from unified agent application 600 including Secure Sockets Layer (SSL) certificates and exceptions. The unified agent application 600 shall indicate that user is connected to security cloud 608, and app statistics shall be populated.

After the user has successfully authenticated (including transparent authentication), the user shall be enrolled with a VPN service and the VPN broker info shall be downloaded by the unified agent application 600 and the VPN tunnel shall be established. The unified agent application 600 can support captive portal detection to fail open when users are behind a captive portal to allow connection to a captive portal.

The unified agent application 600 can forward enterprise internal traffic from the device 604 to the VPN. The unified agent application 600 can recognize when a user goes to an internal app that is provisioned with the VPN service. The unified agent application 600 shall auto enable a tunnel to the VPN service when the user tries connecting to an internal app. The proxy service can always be enforced, and the user is not able to remove it by switching off tunnel or removing the unified agent application 600. Without the proxy solution enforced, the user is not able to access the Internet and would be prompted to restart the web security service, via the unified agent application 600.

The VPN is an on-demand service; unlike the proxy service that shall be enforceable by default, so the user can enable/disable the VPN at will without any password requirements. Once the user logs into the VPN service using a ‘Connect’, the same button shall be labeled ‘Disconnect’ and user shall be able to disconnect the VPN service with a single click. Every time user disconnects with VPN service. The VPN service can be auto-disabled if the user puts their system to sleep mode or there is inactivity (no packets exchanged) after x minutes (x shall be configurable in the VPN settings).

The admin can turn off the proxy service with a single client from an admin UI for a user, all users, or some subset of users. This does not remove the unified agent application 600 from the device 604. A user may be able to disable the proxy service, provided they have the authority and credentials. The unified agent application 600 can provide service related notifications to the user. For example, the unified agent application 600 can provide notifications such as push alerts or the like as well as contain a notification area for a single place to show all notifications that are generated by the proxy service and the VPN service. This shall also include app notifications including configuration updates, agent updates, etc. The user shall be able to clear notifications as well filter notifications from this screen. This shall include a filter for VPN/Proxy, blocked, cautioned, quarantine actions.

Unified Agent Application—Admin Workflow

FIGS. 12 and 13 are screen shots of an admin dashboard (FIG. 12) and a network evaluation configuration (FIG. 13) for the unified agent application 600. An enterprise administrator (admin) can configure the unified agent application 600 for associated users. Configurable parameters generally include the Acceptable Use Policy (AUP), automatic updates, enforcement parameters (e.g., logout password to allow the user to log out of the unified agent application 600, uninstall password to allow the user to uninstall the unified agent application 600, etc.). For the proxy service, the configurable parameters can include Proxy Auto-Config (PAC) per user, group, etc. Also, the proxy service can be enabled for all users, for subsets of users, and/or for individual users. For the VPN service, the configurable parameters can include certificates, IDP servers, ports and protocols, and the like.

The admin dashboard provides a centralized view for all the users of the unified agent application 600, including deployed licenses, device 604 type and Operating System (OS), device policy status, platform type, etc. The network evaluation configuration allows the admin to add a trusted network profile and perform other configurable parameters with the proxy service and the VPN service.

Unified Agent Application—User Workflow

Again, the unified agent application 600 is executed on the device 604. For authentication, the user enters a User ID in the unified agent application 600, such as userid@domain. Subsequently, the unified agent application 600 is configured to discover the services enabled—proxy service and VPN services based on userid@domain. The user authenticates with the presented services, i.e., proxy service, VPN services, and combinations thereof. The unified agent application 600 is auto provisioned for the authenticated service by downloading the service specific configuration. The unified agent application 600 performs the following during VPN enrollment—get the User/Device certificate signed by an Enterprise Intermediate Certificate. This Intermediate Certificate will be same which will be used for signing Assistants. The unified agent application 600 also will pin hardware signatures/fingerprints to the Certificate and user, e.g., Storage Serial ID (Hard Drive Serial ID), CPU ID, Mother Board Serial ID, BIOS serial number, etc.

Unified Agent Application—Authentication and Enrollment Protocol

FIG. 14 is a flowchart of a proxy authentication method 750 to the security cloud 608. For authentication in the proxy service, conventionally, devices 604 can use proxy authentication to register to the security cloud 608. This is not truly reliable as it depends on location/location-authentication policy/VPN and other such factors to work correctly. To simplify this flow, the following new flow can be used with the unified agent application 600 for the method 750. First, the mobile client device 604 initiates an HTTPS request to a CA (e.g., the enterprise CA 618) (step 752). For example, this can be as follows:

login.zscaler.net/clstart?version=1&_domain=nestle.com&redrurl=<url-encoded-url-with-schema>

If the domain is invalid or if the redrurl is missing, CA will reset the connection.

Above end-point begins the client auth flow (step 754). The provided domain is the company that requires the auth. The CA looks up the domain to find the company and their auth mechanism. If the company uses hosted or Active Directory (AD)/Lightweight Directory Access Protocol (LDAP) authentication [SAML auth flow starts at step 760], the response will be a login form with input fields for [username] & [password] (step 756). The form is submitted via POST to the CA at a below end-point:

https://login.zscaler.net/clicred. The HTTP content may look like below

POST/clicred

Host: login.zscaler.net

Content-Length: xyz username=xyz@nestle.com&password=123456&redrurl=<url-encoded-posturl-with-schema>

Next, the CA performs user/password validation and responds with the message explained in step 764 (step 758). If the company uses SAML, response to the request in step 752 will be the SAMLRequest form. The SAMLRequest form will auto-submit to the IDP. Once auth completes, the CA gets control back with the identity of the user. Once SAMLResponse comes back, send the response as a 307 redirect to redrurl with a below format Location: zsa://auth[?token=encrypted-cookie& . . . ] to be appended.

307 query params token = (on success) ecode = (on error) emsg = (on error) On error, send the same redrurl with below format zsa://auth?ecode=<code>&emsg=<message>

FIG. 15 is a flowchart of a VPN authentication method 780 to the security cloud 608. The client (device 604) issues a GET web request to the VPN authentication server with domain name as the query parameter (step 782), such as:

GET //<auth-server>?domain=mockcompany.com

The server identifies the IDP for the given domain and responds with a Hypertext Markup Language (HTML) page containing a SAML Request (step 784). The client will redirect to the IDP with the SAML Request (step 786). The IDP will challenge the client for credentials which can be of the form of username/password or client identity certificate (step 788). On successful authentication, IDP will generate an SAMLResponse for the VPN authentication server (step 790). The client will record the SAMLAssertion for future tunnel negotiation. In the case of error, the server will resend the challenge to the user (step 792).

FIG. 16 is a flowchart of a device enrollment method 800 for the client device 604 and the unified agent application 600. Post successful authentication with all services, in this case, the proxy services, and the VPN services, the client sends an enrollment request to mobile admin (Cloud Administrative Server CAS) (step 802). The request contains device fingerprint and authentication context for each service to identify the user (step 804). For example, the security cloud 608 can use cookies, and the VPN can use SAMLAssertion for the authentication context. The mobile admin (agent management cloud 606) performs inventory lookup with device fingerprints at the MDM server to authorize the user and the device 604 (step 806). On successful authorization, the mobile admin server enrolls the user to cloud services with their authentication contexts (step 808). Each cloud service responds with specific access controls and protocol information that the client receives from mobile admin and uses for local network setup (step 810).

Unified Agent Application—Traffic Interception and Splitting

Again, in order to protect Internet-bound traffic and simultaneously access Enterprise specific Intranet traffic, the device 604 needs to connect through multiple applications. Again, it is not straightforward for users to configure these applications in different networks and different VPN and proxy solutions arise compatibility issues when operating simultaneously. The unified agent application 600 is designed to solve all these issues. The unified agent application 600 handles both proxy (Internet-bound) traffic, and Enterprise Intranet bound traffic. The unified agent application 600 provides secure access to Organizational internal resources when the user is outside of the enterprise network. For Internet-bound traffic, it will forward traffic to the processing node 110 or the cloud node 502, and for Intranet bound traffic, it will forward traffic to a VPN (Broker) or direct if the user is inside the organization network.

The unified agent application 600 is configured to intercept all traffic, specifically to intercept all Transmission Control Protocol (TCP) traffic and DNS traffic before it goes out through the external network interface in the device 604. The unified agent application 600 can intercept other types of traffic as well, such as User Datagram Protocol (UDP). The unified agent application 600 is configured to split traffic at the device 604, i.e., based on a local network configured at the device 604. Split traffic can be as follows: if the VPN service is configured by admin, traffic destined to internal hostnames (configured/provided by company admin) will go to the VPN (broker), if the proxy service is configured by admin, rest of 80/443 traffic will go to the security cloud 608 or will go direct based on PAC file configured by admin, and the remaining traffic will go directly. The unified agent application 600 is configured to send VPN traffic direct for trusted networks (organization's internal network). The unified agent application 600 can also coexist with other VPN clients, i.e., it does not intercept the traffic targeted for those interfaces by specific routes.

Thus, the unified agent application 600 is configured to intercept all traffic at the IP layer for the device 603 or other VPN client's default route. Then, the unified agent application 600 is configured to split traffic to the VPN [for darknet hosted applications], Proxy [for internet-bound cloud services] or Direct [for uninspected traffic] at both the IP or Transport layer.

FIG. 17 is a flowchart of a traffic interception method 820 implemented through the unified agent application 600. The unified agent application 600 registers and sets up a new Network Adapter (TUN interface) on the device (step 822). The unified agent application 600 overrides the device's network default route by configuring the default route of higher priority for the TUN interface (step 824). The unified agent application 600 sets specific route (exact match) for all DNS servers configured on the device 604 with the highest priority (step 826). The unified agent application 600 will not override other specific routes of external adapter or other VPN clients (step 828). The unified agent application 600 will open one UDP listening socket (for all UDP traffic) and two TCP listening sockets (one for VPN traffic and the other for rest of traffic) (step 830).

For each client socket coming to the UDP listening socket port, the unified agent application 600 includes accepting the client socket; if it is a DNS (port 53), a query is performed, else a UDP socket is created (step 832). The query includes if hostname matches one configured by admin for the VPN, the unified agent application 600 will create a local DNS response packet with address a.b.c.d, else it will create a UPD socket, bind it to external Interface and send the DNS packet to the original DNS server, and the response is written back to the client socket. For creating the UDP socket, it is bound to an external interface, a request packet is sent to the original destination server, and a response is written back to the client socket.

For each IP packet coming to the TUN interface, packet processing is performed (step 834). Here, if the packet's source port is equal to any of the unified agent application 600 listening socket's port then, get value corresponding to the packet destination port from the mapping table and replace packet source port with this value, else add a key-value entry <source port, destination port> to a mapping table and replace packet's destination port as per the following rules. If the protocol is UDP, replace with UDP listening socket port, if the protocol is TCP and the destination address is a.b.c.d, replace with the VPN listening socket port, else replace with the second TCP listening socket port. Next, swap the source and destination IP addresses, computer IP and TCP/UDP checksums and overwrite original checksums in the packet, and write modified packet to the external interface.

For example, assume x.x.x.x is the IP address of the TUN interface and zz is the local listening socket port, the following illustrates an example of packet processing:

Original Packet Modified Packet Request packet from client app: Src: y.y.y.y:xx Dest: .x.x.xx:zz Src: x.x.x.x:xx Dest: y.y.y.y:yy Entry added to mapping table: <xx,yy> Response packet from listening socket: Entry fetched from mapping table Src: x.x.x.x:zz Dest: y.y.y.y:xx for key xx is yy Src: y.y.y.y:yy Dest: x.x.x.x:xx

Next, for each client socket coming to the VPN listening socket port, processing is performed (step 836). The processing includes accepting the client socket, if the connection to the VPN is not there, create a socket for the VPN server, bind it to the external interface and connect and authenticate to the VPN; read request data from the socket and write it to the VPN server socket according to VPN protocol, and read response data from VPN socket and write it back to client socket.

For each client socket coming to the second TCP listening socket port, processing is performed (step 838). The processing includes accepting the client socket, if original destination port is 80/443, if the host/IP/URL is bypassed in a PAC file, then create new socket direct to destination server/port, else create new socket (or reuse existing socket) to the security cloud 609 and send connect request for the destination IP and port, else create new socket direct to destination server/port. Once the socket is connected, write request data on it, and when a response is available, write it back to the client socket.

FIG. 18 is a flow diagram of traffic interception and splitting 850 using the unified agent application 600. Again, the unified agent application 600 creates and operates a tunnel (TUN) interface 852 on the device 604. The device 604 includes one or more client applications 854, which can be any program or service executable on the device 604 which requires access to the network interface on the device 604. Traffic for the default route from the client applications 854 is sent to the TUN interface 852, but traffic for specific routes can be sent to other interfaces 856, separate from the TUN interface, for direct connectivity to the Internet 504, such as via VPN services or direct.

The TUN interface 852 splits 858 all traffic. TCP traffic for internal domains is sent to a VPN/broker server 860, TCP port 80/443 traffic is sent to the security cloud 608 for a proxy such as to the processing node 110 or the cloud node 502. Finally, other traffic can be sent directly to the Internet 504. In this manner, the TUN interface 852 operates a local network at the device 604.

FIG. 19 is a flow diagram of example functionality of client applications 864, the TUN interface 852, sockets 862, 864, and the VPN/broker server 860 for the interception and splitting 850 using the unified agent application 600. Specifically, FIG. 19 illustrates activity between the client applications 864, the TUN interface 852, a UDP listening socket 862, a VPN listening socket 864, and the VPN/broker server 860. First, the client application 854 sends a DNS query for an internal domain (step 902). The TUN interface 852 receives the IP packet corresponding to the DNS request and changes the packet's destination to the UDP listening socket 862 and writes the packet back (step 904). The UDP listening socket 862 receives the UDP socket connection, accepts the socket, creates and writes a local DNS response packet with A.B.C.D address (step 906). The DNS response is sent from the UDP listening socket 862 to the TUN interface 852 (step 908) and modified and sent back to the client application 854 (step 910).

Next, the client application 854 opens a TCP socket to A.B.C.D:XX and writes request data (step 912). The TUN interface 852 receives the IP packet corresponding to the TCP socket and changes the packet's destination address to the VPN listening socket 864 and writes the packet back (step 914). The VPN listening socket 864 receives the TCP socket connection, accepts the socket and read request data, and creates the socket through an external interface to connect and authenticate to the VPN server 860 and write TCP request data (step 916). The VPN server 860 sends TCP response data (step 918), the VPN listening socket 864 writes a response back to the client socket (step 920), and the TUN interface 852 modifies the packet and sends TCP response data (step 922).

FIG. 20 is a flow diagram of tunnel forwarding rules 940 by the unified agent application 600. A periodic health monitor function 942 operates, based on a periodic timer 944, to check a PAC ping and a gateway connect ping to provide a state to a bypass fail/open module 946. A network state change function 948 is configured to detect a network change event 950 such as DNS server address, DNS search domains, on-net host DNS lookups, etc., and to provide a state to the bypass fail/open module 946. The bypass fail/open module 946 creates an active tunnel 952 or disabled tunnel 954 based on the states.

Unified Agent Application—MDM Functionality

The unified agent application 600 can further be utilized to perform MDM functionality of the user device 604, in addition to the various other functionality described herein. That is, the unified agent application 600 is in the unique position to provide MDM without the need for a third-part application, third-party service, additional hardware, etc. That is, the unified agent application 600 is required for enterprise service access, and it can double as MDM as well.

FIG. 21 is a flowchart of an MDM method 1000 implemented through the unified agent application 600 and the distributed security system 100 or the cloud system 500. The MDM method 1000 includes an IT administrator configuring MDM policies on the Mobile Admin, i.e., the mobile admin function 650 (step 1002). Here, the IT administrator can specify MDM policies for users, groups of users, etc. associated with an enterprise. For example, the MDM policies can include, without limitation, password configuration, screen lock, remote wipe, enable/disable features such as the browser or camera, application settings, allowed/disallowed applications, delete applications, install applications, etc.

The Mobile Admin notifies the CA, e.g., the authority node 120, with policy metadata (step 1004). Once the CA receives update policy metadata, it pushes it down to all cloud nodes 110, 502 in the distributed security system 100 or the cloud system 500 (step 1006). As described herein, the unified agent application 600 is continuously forwarding traffic to a cloud node 110, 502 (step 1008). The cloud node 110, 502 communicates MDM data via the tunnel (step 1010). In an embodiment, the cloud node 110, 502 can send a 200 OK with a custom HTTP header with MDM data in response to a CONNECT request. The MDM data can include metadata of policy and the payload can be encrypted. In another embodiment, the cloud node 110, 502 can sends metadata to the unified agent application 600 over an encrypted control channel.

This process can be instant or IT Admin can schedule when changes should be applicable. The IT Admin has flexibility to create policy for group(s) or individual user(s) or whole organization.

It will be appreciated that some embodiments described herein may include one or more generic or specialized processors (“one or more processors”) such as microprocessors; Central Processing Units (CPUs); Digital Signal Processors (DSPs): customized processors such as Network Processors (NPs) or Network Processing Units (NPUs), Graphics Processing Units (GPUs), or the like; Field Programmable Gate Arrays (FPGAs); and the like along with unique stored program instructions (including both software and firmware) for control thereof to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the methods and/or systems described herein. Alternatively, some or all functions may be implemented by a state machine that has no stored program instructions, or in one or more Application Specific Integrated Circuits (ASICs), in which each function or some combinations of certain of the functions are implemented as custom logic or circuitry. Of course, a combination of the aforementioned approaches may be used. For some of the embodiments described herein, a corresponding device such as hardware, software, firmware, and a combination thereof can be referred to as “circuitry configured or adapted to,” “logic configured or adapted to,” etc. perform a set of operations, steps, methods, processes, algorithms, functions, techniques, etc. as described herein for the various embodiments.

Moreover, some embodiments may include a non-transitory computer-readable storage medium having computer readable code stored thereon for programming a computer, server, appliance, device, processor, circuit, etc. each of which may include a processor to perform functions as described and claimed herein. Examples of such computer-readable storage mediums include, but are not limited to, a hard disk, an optical storage device, a magnetic storage device, a ROM (Read Only Memory), a PROM (Programmable Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), an EEPROM (Electrically Erasable Programmable Read Only Memory), Flash memory, and the like. When stored in the non-transitory computer readable medium, software can include instructions executable by a processor or device (e.g., any type of programmable circuitry or logic) that, in response to such execution, cause a processor or the device to perform a set of operations, steps, methods, processes, algorithms, functions, techniques, etc. as described herein for the various embodiments.

Although the present disclosure has been illustrated and described herein with reference to preferred embodiments and specific examples thereof, it will be readily apparent to those of ordinary skill in the art that other embodiments and examples may perform similar functions and/or achieve like results. All such equivalent embodiments and examples are within the spirit and scope of the present disclosure, are contemplated thereby, and are intended to be covered by the following claims. 

What is claimed is:
 1. A non-transitory computer readable medium storing computer executable instructions, and in response to execution by the processor in a cloud node, the computer-executable instructions cause a processor to perform the steps of: providing an application to a mobile device for installation and operation thereon, wherein the application is configured for service discovery and connectivity of one or more cloud services, for the mobile device; creating a tunnel to the mobile device via the application for the one or more cloud services; receiving Mobile Device Management (MDM) data from a central authority, wherein the MDM data includes policy metadata specifying MDM functions for mobile devices associated with users of an enterprise; communicating to the application on the mobile device associated with a user, via a tunnel; and providing a 200 OK with a custom HTTP header with the MDM data to the mobile device associated with the user via the tunnel and the application in response to a CONNECT request, wherein the application is configured to implement MDM functions on the mobile device in addition to the service discovery and connectivity of the one or more cloud services, and wherein the application does not call home or subscribe to notification services for scalability and efficiency.
 2. The non-transitory computer readable medium of claim 1, wherein the steps further include: receiving an update to the MDM data from the central authority; and one of instantly communicating the update to the mobile device and communicating the update to the mobile device based on a schedule.
 3. The non-transitory computer readable medium of claim 1, wherein the providing is via an encrypted control channel.
 4. The non-transitory computer readable medium of claim 1, wherein the MDM data specifies any of password configuration, screen lock, remote wipe, enable/disable features, allowed/disallowed applications, deletion of applications, and installation of applications.
 5. The non-transitory computer readable medium of claim 1, wherein the steps further include: authenticating the user into the one or more cloud services via the tunnel.
 6. The non-transitory computer readable medium of claim 1, wherein the application on the mobile device is configured to forward traffic via the tunnel, through the cloud node.
 7. A cloud node comprising: a processor and memory storing instructions that, when executed, cause the processor to providing an application to a mobile device for installation and operation thereon, wherein the application is configured for service discovery and connectivity of one or more cloud services, for the mobile device; creating a tunnel to the mobile device via the application for the one or more cloud services; receive Mobile Device Management (MDM) data from a central authority, wherein the MDM data includes policy metadata specifying MDM functions for mobile devices associated with users of an enterprise; communicate to the application on the mobile device associated with a user, via a tunnel; and provide a custom Hypertext Transfer Protocol (HTTP) header with encrypted payload a 200 OK with a custom HTTP header with the MDM data to the mobile device associated with the user via the tunnel and the application, wherein the application is configured to implement MDM functions on the mobile device in addition to the service discovery and connectivity of the one or more cloud services, and wherein the application does not call home or subscribe to notification services for scalability and efficiency.
 8. The cloud node of claim 7, wherein the instructions that, when executed, further cause the processor to receive an update to the MDM data from the central authority; and one of instantly communicate the update to the mobile device and communicate the update to the mobile device based on a schedule.
 9. The cloud node of claim 7, wherein the MDM data is provided via an encrypted control channel.
 10. The cloud node of claim 7, wherein the MDM data specifies any of password configuration, screen lock, remote wipe, enable/disable features, allowed/disallowed applications, deletion of applications, and installation of applications.
 11. The cloud node of claim 7, wherein the instructions that, when executed, further cause the processor to authenticating the user into the one or more cloud services via the tunnel.
 12. The cloud node of claim 7, wherein the application on the mobile device is configured to forward traffic via the tunnel, through the cloud node.
 13. A method implemented in a cloud node comprising: providing an application to a mobile device for installation and operation thereon, wherein the application is configured for service discovery and connectivity of one or more cloud services, for the mobile device; creating a tunnel to the mobile device via the application for the one or more cloud services; receiving Mobile Device Management (MDM) data from a central authority, wherein the MDM data includes policy metadata specifying MDM functions for mobile devices associated with users of an enterprise; communicating to application on the mobile device associated with a user, via a tunnel, wherein the application is configured for service discovery and connectivity of one or more cloud services; and providing via a custom Hypertext Transfer Protocol (HTTP) header with encrypted payload a 200 OK with a custom HTTP header with the MDM data to the mobile device associated with the user via the tunnel and the application, wherein the application is configured to implement MDM functions on the mobile device in addition to the service discovery and connectivity of the one or more cloud services, and wherein the application does not call home or subscribe to notification services for scalability and efficiency.
 14. The method of claim 13, further comprising receiving an update to the MDM data from the central authority; and one of instantly communicating the update to the mobile device and communicating the update to the mobile device based on a schedule.
 15. The method of claim 13, wherein the providing is via an encrypted control channel.
 16. The method of claim 13, wherein the MDM data specifies any of password configuration, screen lock, remote wipe, enable/disable features, allowed/disallowed applications, deletion of applications, and installation of applications.
 17. The method of claim 13, further comprising: authenticating the user into the one or more cloud services via the tunnel. 